Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| "2023-08-22T10:21:00", | ||
| "2023-08-22" | ||
| ], | ||
| "description": "In Codat's data model, dates and times are represented using the <a class=\"external\" href=\"https://en.wikipedia.org/wiki/ISO_8601\" target=\"_blank\">ISO 8601 standard</a>. Date and time fields are formatted as strings; for example:\n\n```\n2023-08-22T10:21:00\n2023-08-22\n```\n\nWhen pushing bank transaction data to Codat, the date is treated as a local date. This means:\n\n- The date/time is used exactly as provided, without any timezone conversion.\n- If a timezone offset is included (e.g., `2023-08-22T10:21:00-05:00`), the offset will be ignored and only the local date/time portion will be used.\n- We recommend providing dates without a timezone suffix for clarity (e.g., `2023-08-22T10:21:00` rather than `2023-08-22T10:21:00Z`)." |
There was a problem hiding this comment.
Timezone offsets silently ignored in transaction dates
High Severity
The date field now silently ignores timezone offsets in ISO 8601 timestamps, treating 2023-08-22T10:21:00-05:00 and 2023-08-22T10:21:00+05:00 as identical times despite being 10 hours apart. This violates ISO 8601 semantics and can cause incorrect transaction ordering when clients submit transactions from different timezones, leading to data integrity issues in bank transaction records.
Additional Locations (1)
1 participant
Updated OAS at 2026-01-23T09:38:54Z
Note
Low Risk
Spec- and example-only changes; risk is limited to client integrations that rely on the previous
dateformat or example shapes when generating code.Overview
Updates the published OAS specs to add an optional
isRecurringboolean on enhanced/categorized bank transaction objects, indicating whether Codat’s categorization engine marked the transaction as recurring.Refines the Bank Feeds schema for
BankTransactions.dateto be an ISO-8601 local date/time string (no timezone conversion), and updates request/response examples to remove the trailingZ. Also adjusts categorized transaction examples to nest category details undertransactionCategoryand includesisRecurringvalues in sample payloads.Written by Cursor Bugbot for commit daaaac0. This will update automatically on new commits. Configure here.